Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).cdr { purge { storage-limit storage_limit | time-limit time_limit } [ max-files max_records_to_purge ] | push-interval push_interval | push-trigger space-usage-percent trigger_percentage | remove-file-after-transfer | transfer-mode { pull [ module-only ] | push primary { encrypted-url encrypted_url | url url } [ [ max-files max_records ] [ module-only ] [ secondary { encrypted-secondary-url encrypted_secondary_url | secondary-url secondary_url } ] [ via local-context ] + ] | use-harddisk }
|
•
|
purge: Disabled
|
|
•
|
push-interval: 300 seconds
|
|
•
|
push-trigger: 80 percent
|
|
•
|
remove-file-after-transfer: Disabled
|
|
•
|
transfer mode: Pull
|
|
•
|
push via: line card is used for push
|
|
•
|
use-harddisk: Disabled
|
Important: The use-harddisk keyword is only available on ASR 5000 chassis.|
•
|
purge: Disables purging of records.
|
|
•
|
remove-file-after-transfer: Retains a copy of the file even after it has been pushed or pulled to another server.
|
|
•
|
use-harddisk: Disables data storage on the SMC hard disk.
|
Important: The use-harddisk keyword is available only on the ASR 5000 chassis.|
•
|
storage-limit storage_limit: Specifies to start deleting files when the specified megabytes of space is used for storage.
|
storage_limit specifies the volume limit for the record files, in megabytes, and must be an integer from 10 through 143360.
|
•
|
time-limit time_limit: Specifies to start deleting files older than the specified time limit.
|
time_limit specifies the time limit for the record files, and must be an integer from 600 through 2592000.
|
•
|
max-files max_records_to_purge: Specifies the maximum number of records to purge.
|
max_records_to_purge must be an integer from 1000 through 10000.
push-interval value
value must be an integer from 60 through 3600.
push-trigger space-usage-percent trigger_percentage
trigger_percentage specifies the UDR/EDR disk utilization percentage for triggering push, and must be an integer from 10 through 80.
transfer-mode { pull [ module-only ] | push primary { encrypted-url encrypted_url | url url } [ [ max-files max_records ] [ module-only ] [ secondary { encrypted-secondary-url encrypted_secondary_url | secondary-url secondary_url } ] [ via local-context ] + ]
|
•
|
pull: Specifies that the L-ESS is to pull the CDR files.
|
|
•
|
push: Specifies that the system is to push CDR files to the configured L-ESS.
|
|
•
|
max-files max_records: Specifies the maximum number of files sent per iteration based on configured file size.
|
|
•
|
module-only: Specifies that the transfer-mode is only applicable to the UDR module; if not configured it is applicable to both EDR and UDR modules. This enables support for individual record transfer-mode configuration for each module.
|
|
•
|
primary encrypted-url encrypted_url: Specifies the primary location in encrypted format to which the system pushes the CDR files.
|
encrypted_url must be the primary location name in an encrypted format, and must be an alphanumeric string of 1 through 1024 characters.
|
•
|
primary url url: Specifies the primary location to which the system pushes the CDR files.
|
url must be the primary location, and must be an alphanumeric string of 1 through 1024 characters in the format: //user:password@host:[port]/directory.
|
•
|
secondary encrypted-secondary-url encrypted_secondary_url: Specifies the secondary location in encrypted format to which the system pushes the CDR files when the primary location is unreachable or fails.
|
encrypted_secondary_url must be the location in an encrypted format, and must be an alphanumeric string of 1 through 1024 characters.
|
•
|
secondary secondary-url secondary_url: Specifies the secondary location to which the system pushes the CDR files when the primary location is unreachable or fails.
|
secondary_url must be the secondary location, and must be an alphanumeric string of 1 through 1024 characters in the format: //user:password@host:[port]/directory.
|
•
|
via local-context: Selects the LC/SPIO for transfer of CDRs. The system pushes the UDR files via SPIO in the local context.
|
Important: The use-harddisk keyword is available only on the ASR 5000 chassis.The cdr use-harddisk command is available only on the ASR 5000 chassis. This command can be run only in a context where CDRMOD is running. Configuring in any other context will result in failure with the message “Failure: Please Check if CDRMOD is running in this context or not.”
The cdr use-harddisk command can be configured either in the UDR or EDR module, but will be applicable to both record types. Configuring in one of the modules will prevent the configuration to be applied in the other module. Any change to this configuration must be done in the module in which it was configured, the change will be applied to both record types.
The VPNMgr can send a maximum of 4000 files to the remote server per iteration. However if the individual file size is big (say when compression is not enabled), then while transferring 4000 files SFTP operation takes a lot of time. To prevent this, the cdr transfer-mode push command can be configured with the keyword max-files, which allows operators to configure the maximum number of files sent per iteration based on configured file size.
file [ charging-service-name { include | omit } ] [ compression { gzip | none } ] [ current-prefix string ] [ delete-timeout seconds ] [ directory directory_name ] [ exclude-checksum-record ] [ field-separator { hyphen | omit | underscore } ] [ file-sequence-number rulebase-seq-num ] [ headers ] [ name file_name ] [ reset-indicator ] [ rotation [ num-records number | time seconds | volume bytes ] ] [ sequence-number { length length | omit | padded | padded-six-length | unpadded } ] [ storage-limit limit ] [ time-stamp { expanded-format | rotated-format | unix-format } ] [ trailing-text string ] [ trap-on-file-delete ] [ udr-seq-num ] [ xor-final-record ] +
Configures the default setting for the specified keyword(s). Using the default file command will reset some but not all keyword parameters to their default values. To ensure that the default is reset for a specific parameter, include the corresponding keyword in the command.
|
•
|
include: Includes name of the charging service in the UDR file name.
|
|
•
|
omit: Excludes name of the charging service in the UDR file name.
|
Default: include
|
•
|
gzip: Enables GNU zip compression of the UDR file at approximately 10:1 ratio.
|
|
•
|
none: Disables Gzip compression.
|
Default: none
current-prefix string
string must be an alphanumeric string of 1 through 31 characters.
delete-timeout seconds
seconds must be an integer from 3600 through 31536000.
directory directory_name
directory_name must be an alphanumeric string of 1 through 191 characters.
|
•
|
hyphen: Specifies to use ‘-’ (hyphen) as the field separator.
|
|
•
|
omit: Excludes the field separator.
|
|
•
|
underscore: Specifies to use ‘_’ (underscore) as the field separator.
|
Default: underscore
name file_name
file_name must be an alphanumeric string of 1 through 31 characters. The file name format is as follows:
|
•
|
base: Specifies type of record in file or contains the operator-specified string. Default: udr
|
|
•
|
rulebase: Specifies the name of the ACS rulebase. UDRs from different rulebases go into different UDR files.
|
|
•
|
format: Specifies the name of the UDR format if single-udr-format is specified, else the format field (and the trailing underscore) is omitted from the file name.
|
|
•
|
sequencenum: This is a 5-digit sequence number to detect the missing file sequence. It is unique among all UDR files on the system.
|
|
•
|
timestamp: Contains a timestamp based on file creation time in UTC formatted as: MMDDYYYYHHMMSS.
|
File name for a UDR file in CSV format that contains information for a rulebase named rulebase1 and a UDR schema named udr_schema1 appears as follows:
|
•
|
basename: A global-based configurable text string that is unique per system that uniquely identifies the global location of the system running ACS.
|
|
•
|
ChargSvcName: A system context-based configurable text string that uniquely identifies a specific context-based charging service.
|
|
•
|
timestamp: Date and time at the instance of file creation. Date and time in the format: “MMDDYYYYHHmmSS”, where HH is a 24-hour value from 00-23.
|
|
•
|
SeqNumResetIndicator: A one-byte counter used to discern the potential for duplicated FileSeqNumber with a range of 0 through 255, which is incremented by a value of 1 for the following conditions:
|
|
•
|
FileSeqNumber: unique file sequence number for the file is a 9-digit integer from 000000000 through 999999999. It is unique on each chassis.
|
File name for a closed xDR file in CSV format that contains information for ACS xyz_city1 and charging service name preapaid2 with timestamp 12311969190000, and file sequence number counter reset indicator to 002 for file sequence number 034939002 appears as follows:
File name for a running xDR file in CSV format that contains information for the same parameters for file sequence number 034939003 prefixed with curr_ and appears as follows:
|
•
|
num-records records: Specifies the number of records that should be added to the file. When the number of records in the file reaches this specified value, the file is complete.
|
records must be an integer from 100 through 10240.
|
•
|
time seconds: Specifies the period of time to wait before closing the UDR file and creating a new one.
|
seconds must be an integer from 30 through 86400.
|
•
|
volume bytes: Specifies the maximum size of the UDR file before closing it and creating a new one.
|
bytes must be an integer from 51200 through 62914560.
Note that higher settings may provide the best compression ratio when the compression keyword is set to gzip.
|
•
|
length length: Includes the sequence number with the specified length.
|
length must be the length of the file sequence number with preceding zeroes in the file name, and must be an integer from 1 through 9.
Important: The length configuration is applicable in both UDR and EDR modules. When applied in both modules without the file udr-seq-num configuration, the minimum among the two values will come into effect for both modules. With the file udr-seq-num config, each module will use its own value of length.|
•
|
omit: Excludes the sequence number from the file name.
|
|
•
|
padded: Includes the padded sequence number with preceding zeros in the file name. This is the default setting.
|
|
•
|
padded-six-length: Includes the padded sequence number with six preceding zeros in the file name.
|
|
•
|
unpadded: Includes the unpadded sequence number in the file name.
|
Default: padded
storage-limit limit
On an ASR 5000 chassis, limit must be an integer from 10485760 through 536870912.
Important: On the ASR 5000 chassis, the total storage limit is 536870912 bytes (512 MB). This limit is for both UDR and EDR files combined.|
•
|
expanded-format: Specifies the UTC MMDDYYYYHHMMSS format.
|
|
•
|
rotated-format: Specifies the YYYYMMDDHHMMSS format.
|
|
•
|
unix-format: Specifies the UNIX format of x.y, where x is the number of seconds since 1/1/1970 and y is the fractional portion of the current second that has elapsed.
|
trailing-text string
string must be an alphanumeric string of 1 through 30 characters.
Specifies inserting an XOR checksum (in place of the CRC checksum) into the UDR file header if the exclude-checksum-record keyword is left at its default setting.
